T2b APPROVE — root cause and fix verified:

Root cause: StorylineCreated hardcodes plot_count:1 then inserts genesis plot, but never reconciles — unlike PlotChained which calls reconcileStorylinePlotCount(). Result: cached plot_count drifts +1.

Fix: Add reconcileStorylinePlotCount() after genesis plot upsert in both:

• src/app/api/index/storyline/route.ts (live indexer) ✓
• src/app/api/cron/backfill/route.ts (backfill cron) ✓

Import added only where missing (storyline route); backfill already had it. Reuses existing reconcile function — no new abstractions. Reading Mode unaffected (counts chapters directly). +7 lines, 0 deletions. Minimal and correct.

Verdict: REQUEST CHANGES

Summary

The root-cause analysis looks right, but this patch only fixes future StorylineCreated ingests. Existing storylines with inflated plot_count values will stay wrong after merge.

Findings

• [high] The backfill cron still resumes from backfill_cursor.last_block, so the new reconcileStorylinePlotCount() only runs for brand-new or explicitly replayed StorylineCreated events. Production storylines that were already indexed before this patch are never revisited, which means the globally wrong storyline.plot_count values on profile/story/card surfaces remain wrong even after deployment.
  • File: src/app/api/cron/backfill/route.ts:110
  • Suggestion: add an explicit one-off reconciliation for existing storylines, or intentionally replay the affected historical range as part of the fix so current rows are corrected, not just future inserts.

Decision

Requesting changes because issue #739 is a global existing-data bug, and this PR currently prevents new drift without repairing the rows that are already wrong.

Verdict: REQUEST CHANGES

Summary

The new reconcile endpoint repairs existing bad rows, but it is exposed without the cron authorization guard used by the other maintenance routes.

Findings

• [high] POST /api/cron/reconcile-plots is unauthenticated. Unlike the existing cron/backfill route, this new endpoint does not check CRON_SECRET or any auth header before iterating every storyline and issuing server-side updates. That means any external caller can trigger a full-database reconciliation job on demand.
  • File: src/app/api/cron/reconcile-plots/route.ts:12
  • Suggestion: apply the same cron authorization pattern used in src/app/api/cron/backfill/route.ts before running the reconciliation loop.

Decision

Requesting changes because the data-fix direction is right, but the new maintenance endpoint needs the existing cron auth guard before it is safe to merge.

Verdict: REQUEST CHANGES

Summary

The code-level blockers are resolved, but issue #739 still has no ticket comment documenting the root cause.

Findings

• [medium] Issue #739 explicitly requires the root cause to be documented in the ticket comments, but the issue currently has no comments. The PR summary explains it, but the acceptance criterion is still unmet.
  • File: issue #739 comments
  • Suggestion: post the root-cause summary to issue #739 before merge so the fix is documented where the ticket asked for it.

Decision

Keeping this as request changes because the implementation looks correct now, but the ticket’s documentation requirement is still incomplete.

Verdict: APPROVE

Summary

The remaining documentation blocker is resolved. Issue #739 now has the required root-cause comment, and the code changes cover both future ingests and existing storyline reconciliation.

Findings

• None.

Decision

Approving because the review blockers are addressed and the ticket requirements are now complete.